can't detect the z axis of the joystick via directinput

Question

0.00/5 (No votes)

See more:

I am doing something about the joystick, all I want to do is to access the value of the x,y,z axis, and now I have got the x y axis value already, but I can't even detect z axis, and can't get the value of z axis, what should i do?

Posted 24-Apr-11 22:33pm

robotics_study

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-04-24T22:40:00

Solution 1

There is absolutely nothing special about Z axis.

You Z axis can be rotational or not implemented in your device; or you mixed up Z axis with another degree of freedom such as rudder (which has a different API in DirectX input library (do you use DirectX?)). It can be a result of some bug. It's hard to say anything else based on your information.

—SA

Posted 24-Apr-11 22:40pm

Sergey Alexandrovich Kryukov

Comments

robotics_study 25-Apr-11 5:02am

I called GetDeviceState(), and got the value of x and y axis from the structure of DIJOYSTATE, but the z axis and the button information could not be accessed. I have these sentences:
if(pdidoi->guidType==GUID_XAxis) AfxMessageBox("x_axis");
if(pdidoi->guidType==GUID_YAxis) AfxMessageBox("y_axis");
if(pdidoi->guidType==GUID_ZAxis) AfxMessageBox("z_axis");
and the pdidoi is a pointer to DIDEVICEOBJECTINSTANCE, run the program, "y_axis" and "x_axis" have appeared, but "z_axis" not. Could you tell me the reasons? Thanks a lot!

Sergey Alexandrovich Kryukov 25-Apr-11 5:37am

What is Z in device, physically? It could be a different degree of freedom, all I can think of for now.
Move all axis and look for DIJOYSTATE or DIJOYSTATE2.
I don't see guidType member; you need to use DIJOYSTATE.x, DIJOYSTATE.y, etc. Just dump all the structure is some text, write into text edit control and watch what really changed in the structure.
--SA

robotics_study 26-Apr-11 22:10pm

I have done those you said. And I use DIJOYSTATE.lX,lY,and lZ, only lX,and lY can have values, while the lZ is always zero. I am puzzled. Can you give me your email, and I send my progect to you. And do me a favor to check my code, thanks a lot!

Sergey Alexandrovich Kryukov 26-Apr-11 22:45pm

You see, I don't have any joystick at the moment; without it won't help much. I remember I got it all from the first attempt -- 3D joystick with .NET 2.0.
My web site has "contact me" page, see my profile.
--SA

Sergey Alexandrovich Kryukov 26-Apr-11 22:47pm

My idea way: dump this structure to the screen ***in full***, every single member of it; watch it while moving the joystick.
--SA

robotics_study 27-Apr-11 21:17pm

Thanks for your advice, and I have already done these before. Values of x and y axis are displayed on the dialog once thirty millisenconds, but I can't get the value of z axis.

Sergey Alexandrovich Kryukov 27-Apr-11 21:53pm

Wait, wait, this is something... what, you do it by timer? It's wrong. It supports interrupt-oriented way: it accepts an instance if EventWaitHandle and set it every time the status is changed. You should have a thread and call EventWaitHandle.WaitOne() in a loop and notify changed data after waking up by the set handle (but ultimately by a hardware interrupt). While at wait state, the thread uses zero CPU time until awakened. You need to use Dispatcher.Invoke or Dispatcher.BeginInvoke to notify UI thread (you cannot call any UI methods/properties from non-UI thread).

How could you miss it? This is most important part. I'm not sure it will fix your problem, but what are your doing is wrong. Maybe, your event-less polling spoils something due to race condition or something. Anyway, you need to do right thing.

--SA